- Main Page
- Information on the Institution
- General Description of the Institution
- Address of İzmir University of Economics
- Academic Authorities
- Academic Calendar
- Recognition of Prior Learning
- Recognition of Study Abroad
- List of Programs Offered
- General Admission Requirements
- General Registration Procedures
- ECTS Credit Allocation
- Grading
- Arrangements for Academic Guidance
- Internationalization
- Institutional ECTS Coordinator
- Departmental Erasmus Coordinators
- Degree Programs
- Software Engineering
- Qualification Awarded
- Level of Qualification
- Specific Admission Requirements
- Qualification Requirements and Regulations
- Recognition of Prior Learning
- Profile of the Program
- Program Outcomes
- Course & Program Outcomes Matrix
- Occupational Profiles of Graduates
- Access to Further Studies
- Program Structure
- Course Structure Diagram with Credits
- Exam Regulations & Assessment & Grading
- Graduation Requirements
- Mode of Study
- Program Director (or Equivalent)
- Evaluation Questionnaires
- Courses
- General Information For Students
- About İzmir
- Cost of Living
- Accommodation
- Meals
- Medical Facilities
- Facilities for Special Needs Students
- Career Guidance Center
- Insurance
- Financial Support for Students
- Registrar's Office
- Learning Facilities
- International Programs
- Practical Information for Exchange Students
- Language Courses
- Internships
- Sports and Leisure Facilities
- Student Associations
- Useful Phone Numbers
- Diploma Supplement
- Erasmus Policy Statement
- National Qualifications
- Bologna Commission
11111
COURSE INTRODUCTION AND APPLICATION INFORMATION
se.cs.ieu.edu.tr
| Course Name | |
| Code | Semester | Theory (hour/week) | Application/Lab (hour/week) | Local Credits | ECTS |
|---|---|---|---|---|---|
| Fall/Spring |
| Prerequisites | None | |||||
| Course Language | ||||||
| Course Type | Elective | |||||
| Course Level | - | |||||
| Mode of Delivery | - | |||||
| Teaching Methods and Techniques of the Course | ||||||
| Course Coordinator | ||||||
| Course Lecturer(s) | ||||||
| Assistant(s) | - | |||||
| Course Objectives | |
| Learning Outcomes | The students who succeeded in this course;
|
| Course Description |
|
| Core Courses | X |
| Major Area Courses | ||
| Supportive Courses | ||
| Media and Managment Skills Courses | ||
| Transferable Skill Courses |
WEEKLY SUBJECTS AND RELATED PREPARATION STUDIES
| Week | Subjects | Required Materials |
| 1 | Introduction, IEEE Std 1219 | |
| 2 | The context of maintenance, introduction to the basic concepts | Grubb and Takang, ch.1 |
| 3 | The maintenance framework. | Grubb and Takang, ch.2, Pressman, ch. 29 |
| 4 | Software change | Grubb and Takang, ch.3 |
| 5 | Limitations and economic implications to software change | Grubb and Takang, ch.4 |
| 6 | Maintenance process | Grubb and Takang, ch.5, ISO/IEC 14764 |
| 7 | Overview | |
| 8 | Midterm exam | |
| 9 | Program understanding | Grubb and Takang, ch.6 |
| 10 | Reverse engineering | Grubb and Takang, ch.7 |
| 11 | Reverse engineering | Grubb and Takang, ch.7 |
| 12 | Reuse and resuability | Grubb and Takang, ch.8 |
| 13 | Reuse and reusability | Grubb and Takang, ch.8 |
| 14 | Management and organizational issues | Grubb and Takang, ch.10 |
| 15 | General Evaluation | |
| 16 | Review of the Semester |
| Course Notes/Textbooks | Grubb and Takang, Software Maintenance Concepts and Practice, 2e, World Scientific, 2003. |
| Suggested Readings/Materials | Sommerville, Software Engineering, 9e, AddisonWesley, 2011. * Pressman, Software Engineering: A Practitioners Approach, 7e, McGrawHill, 2010. * SWEBOK, Guide to the Software Engineering Body of Knowledge: 2004, IEEE. * April, Abran & Dumke, What do you need to know about Software Maintenance?, Maintenance and assest management, 2005, vol. 20, no 2, pp. 3237. * Lanubile and Visaggio, Iterative Reengineering to compensate for QuickFix Maintenance, IEEE, 1995, International Conference on Software Maintenance, pp.140146. * Canfora and Cimitile, Software Maintenance, 2000, http://www.compaid.com/caiInternet/ezine/maintenancecanfora.pdf.* Jones, The Economics of Software Maintenance in the Twenty First Century, 2006. |
EVALUATION SYSTEM
| Semester Activities | Number | Weigthing |
| Participation | ||
| Laboratory / Application | ||
| Field Work | ||
| Quizzes / Studio Critiques | 1 | 20 |
| Portfolio | ||
| Homework / Assignments | ||
| Presentation / Jury | ||
| Project | ||
| Seminar / Workshop | ||
| Oral Exam | ||
| Midterm | 1 | 30 |
| Final Exam | 1 | 50 |
| Total |
| Weighting of Semester Activities on the Final Grade | 50 | |
| Weighting of End-of-Semester Activities on the Final Grade | 50 | |
| Total |
ECTS / WORKLOAD TABLE
| Semester Activities | Number | Duration (Hours) | Workload |
|---|---|---|---|
| Course Hours (Including exam week: 16 x total hours) | 16 | 3 | 48 |
| Laboratory / Application Hours (Including exam week: 16 x total hours) | 16 | ||
| Study Hours Out of Class | 15 | 3 | |
| Field Work | |||
| Quizzes / Studio Critiques | 1 | 5 | |
| Portfolio | |||
| Homework / Assignments | |||
| Presentation / Jury | |||
| Project | |||
| Seminar / Workshop | |||
| Oral Exam | |||
| Midterms | 1 | 7 | |
| Final Exams | 1 | 15 | |
| Total | 120 |
COURSE LEARNING OUTCOMES AND PROGRAM QUALIFICATIONS RELATIONSHIP
| # | Program Competencies/Outcomes | * Contribution Level | ||||
1 | 2 | 3 | 4 | 5 | ||
| 1 | Be able to define problems in real life by identifying functional and nonfunctional requirements that the software is to execute | X | ||||
| 2 | Be able to design and analyze software at component, subsystem, and software architecture level | X | ||||
| 3 | Be able to develop software by coding, verifying, doing unit testing and debugging | X | ||||
| 4 | Be able to verify software by testing its behaviour, execution conditions, and expected results | X | ||||
| 5 | Be able to maintain software due to working environment changes, new user demands and the emergence of software errors that occur during operation | X | ||||
| 6 | Be able to monitor and control changes in the software, the integration of software with other software systems, and plan to release software versions systematically | X | ||||
| 7 | To have knowledge in the area of software requirements understanding, process planning, output specification, resource planning, risk management and quality planning | X | ||||
| 8 | Be able to identify, evaluate, measure and manage changes in software development by applying software engineering processes | X | ||||
| 9 | Be able to use various tools and methods to do the software requirements, design, development, testing and maintenance | X | ||||
| 10 | To have knowledge of basic quality metrics, software life cycle processes, software quality, quality model characteristics, and be able to use them to develop, verify and test software | X | ||||
| 11 | To have knowledge in other disciplines that have common boundaries with software engineering such as computer engineering, management, mathematics, project management, quality management, software ergonomics and systems engineering | X | ||||
| 12 | Be able to grasp software engineering culture and concept of ethics, and have the basic information of applying them in the software engineering | X | ||||
| 13 | Be able to use a foreign language to follow related field publications and communicate with colleagues | X | ||||
*1 Lowest, 2 Low, 3 Average, 4 High, 5 Highest